-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove telegraf and use only fluent-bit for telemetry #1030
base: main
Are you sure you want to change the base?
Conversation
This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This PR was closed because it has been stalled for 12 days with no activity. |
This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This PR was closed because it has been stalled for 12 days with no activity. |
PR Description
fluent-bit
2.1.10
->3.2.2
(latest)>=3.2
is necessary for usingmetrics_selector
andlabels
processors for filtering Prometheus metrics2.1.10
->3.0.7
(latest)3.0
is the latest Windows versiontelegraf
for Linux and Windowsfluent-bit
prometheus_scrape
input plugin to scrape Prometheus metrics previously collected by telegrafmetrics_selector
andlabels
processors to filter certain metrics and drop unnecessary labels before sending to App Insightsmetrics_selector
andlabels
processorsgithub.com/shirou/gopsutil/v4/process
proxy_plugin
file so that the Prometheus metrics will be allowed to flow to our golang output plugin:out->event_type = FLB_OUTPUT_LOGS | FLB_OUTPUT_METRICS;
fluent-bit
has theproxy_plugin
files to allow the golang output plugins to be built upon the C code. However, this does not specify what type the output plugin accepts (out oflogs
,metrics
, andtraces
types), so it defaults to only allowing thelogs
type to be routed to the ouput plugin.fluent-bit
with the line added above in the exact same way Mariner builds the package.fluent-bit
with the plugins that we actually use so that our CVE surface area is very low.network-observability
andacstor
that was missedNew Feature Checklist
Telemetry Values Comparison